X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C83D11.D2613201@onstor-exch02.onstor.net>; Wed, 12 Dec 2007 14:53:33 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Directory and file name cleanup (ex. agile)
Date: Wed, 12 Dec 2007 14:53:33 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E07099F9A@onstor-exch02.onstor.net>
In-Reply-To: <20071212130803.1f3558ea@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Directory and file name cleanup (ex. agile)
Thread-Index: Acg9AxVhq9uNBGoHTpOwC7goI0MZpQADm2zw
From: "Paul Hammer" <paul.hammer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	<dl-designreview>

What problem will this solve? We have no requirement to do this,
recommend that we just leave it.

-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, December 12, 2007 1:08 PM
To: dl-designreview
Subject: Directory and file name cleanup (ex. agile)

I have prepared a changelist that cleans up the use of the word 'agile'
in file and directory names, and also removes /usr/local/agile from our
software.  Here are the details:

1. /usr/local/agile as a directory has not existed now for several
releases, so it's time to eradicate it.  Change all references to that
directory to /onstor where the files really live.

2. agile.conf is a dead file, remove references to it and remove it
from the build.

3. /var/agile will be split into two different directories: /var/onstor
for trace files and core dumps (although there is some claim core dumps
go in /var/run anyway); and /var/log/onstor for log files, including the
elog messages file, which will now be /var/log/onstor/messages.  This is
because /var/agile had become an arbitrary dumping ground without any
paradigm or logically intuitive organization.


Scope:

All work necessary to complete this should already be done and viewable
in the changelist 26643.  There should be no extra changes necessary by
anyone else, except of course documentation changes.  If you see
something is missing, please inform me.

Timeline:

This will go into the release following R98 as well as Cougar, so
the soonest it will hit customers is in about 3.5 months.  The idea is
to get some general use testing of the change in Development, QA and
Support to fine tune any rough spots prior to release.  In addition the
3 months should and provide plenty of acclimation time.

Data points:

Upgrading.  This may require that we obsolete the previous upgrade
method (system upgrade), and all upgrades for S-W use the upgrade
script.

Implications for data warehouse?  Should be none, but ....
